home *** CD-ROM | disk | FTP | other *** search
- Path: solon.com!not-for-mail
- From: seebs@solutions.solon.com (Peter Seebach)
- Newsgroups: comp.lang.c
- Subject: Re: Why is C faster than FORTRAN?
- Date: 5 Apr 1996 12:01:19 -0600
- Organization: Usenet Fact Police (Undercover)
- Message-ID: <4k3n5f$l5s@solutions.solon.com>
- References: <1996Mar20.132506.91237@ucl.ac.uk> <4jpabs$4pv@opal.southwind.net> <danpop.828650092@rscernix>
- Reply-To: seebs@solon.com
- NNTP-Posting-Host: solutions.solon.com
-
- In article <danpop.828650092@rscernix>, Dan Pop <danpop@mail.cern.ch> wrote:
- >Once upon a time this approach used to work. For a modern processor,
- >be it Pentium (Pro) or any RISC flavour, only a wizard could tell which
- >assembly code sequence is faster simply by looking at the code. The rest
- >of us mere mortals are condemned to benchmarking the compiler output in
- >order to decide which is more efficient.
-
- Further, unless the languages are basically identical, and the optimizers are
- very similar, the chances are that each program solves a fundementally
- different problem, and that there will be no simple correspondance between the
- two assebly outputs.
-
- Even if the compiler can produce assembler; I've had at least one which
- produced different object code for C->assembly->object than it did for
- C->intermediate form->object. In which case, of course, you can't tell much
- from the assembler (which was, if memory serves, slightly worse.)
-
- -s
- --
- Peter Seebach - seebs@solon.com - Copyright 1996 Peter Seebach.
- C/Unix wizard -- C/Unix questions? Send mail for help. No, really!
- FUCK the communications decency act. Goddamned government. [literally.]
- The *other* C FAQ - http://www.solon.com/~seebs/c/c-iaq.html
-